safer git sha object filename
authorJoey Hess <joeyh@joeyh.name>
Tue, 4 Mar 2025 18:54:13 +0000 (14:54 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 4 Mar 2025 18:54:13 +0000 (14:54 -0400)
commita2fc471e14a9fcccb15e5265f6964b8a71b0399a
tree87df9dd35f8e78c0ad48ea29801d0d7c1f5c91b2
parent1ee4d018f3e03de1e06f99a6dd2138c6141c864c
safer git sha object filename

Rather than use the filename provided by INPUT, which could come from user
input, and so could be something that looks like a dashed parameter,
use a .git/object/<sha> filename.

This avoids user input passing through INPUT and back out, with the file
path then passed to a command, which could do something unexpected with
a dashed parameter, or other special parameter.

Added a note in the design about being careful of passing user input to
commands. They still have to be careful of that in general, just not in
this case.
Remote/Compute.hs
doc/design/compute_special_remote_interface.mdwn